home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Base Documentation 1998 November
/
IRIX 6.5.2 Base Documentation November 1998.img
/
usr
/
share
/
catman
/
u_man
/
cat1
/
dhcp_bootp.z
/
dhcp_bootp
Wrap
Text File
|
1998-10-30
|
29KB
|
595 lines
ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM)))) ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM))))
NNNNAAAAMMMMEEEE
dhcp_bootp - proclaim server for Dynamic Host Configuration Protocol
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
////uuuussssrrrr////eeeettttcccc////ddddhhhhccccpppp____bbbboooooooottttpppp [ ----ffffdddd ] [ ----oooo _d_h_c_p__o_p_t_i_o_n_s__f_i_l_e ]
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
_d_h_c_p__b_o_o_t_p is the server that communicates with other DHCP and
_p_r_o_c_l_a_i_m(1M) clients to provide configuration parameters, including at
least an IP address. The format of DHCP messages is based on _b_o_o_t_p
messages (see RFC 951). A detailed protocol specification for DHCP is
contained in RFC 1541, available from the Network Information Center.
The DHCP protocol uses UDP/IP as its transport mechanism. The DHCP
server receives service requests at the UDP port indicated in the _b_o_o_t_p
service description contained in the file /_e_t_c/_s_e_r_v_i_c_e_s (see
_s_e_r_v_i_c_e_s(4)). The _p_r_o_c_l_a_i_m server can be used together with one or more
_p_r_o_c_l_a_i_m _r_e_l_a_y-_a_g_e_n_t_s (see _d_h_c_p__r_e_l_a_y(1M)) to enable clients to obtain
address-leases across networks. The _d_h_c_p__b_o_o_t_p server responds to
multiple interfaces on a multihomed gateway machine, for dynamic IP
addresses.
_d_h_c_p__b_o_o_t_p replaces the standard _b_o_o_t_p(1M) server application and serves
both _b_o_o_t_p and DHCP clients.
CCCCOOOOMMMMMMMMAAAANNNNDDDD LLLLIIIINNNNEEEE OOOOPPPPTTTTIIIIOOOONNNNSSSS
----ffff This enables cross network forwarding if the client is requesting
for service from a dhcp server which is reachable via this server
and on a different wire.
----dddd This enables the _d_h_c_p__s_e_r_v_e_r into a debug mode in which it logs
messages to /_v_a_r/_a_d_m/_S_Y_S_L_O_G.
----oooo The path of the _d_h_c_p__o_p_t_i_o_n_s__f_i_l_e can be mentioned using this
option. The default location is /_e_t_c/_c_o_n_f_i_g/_d_h_c_p__b_o_o_t_p._o_p_t_i_o_n_s.
CCCCOOOONNNNFFFFIIIIGGGGUUUURRRRAAAATTTTIIIIOOOONNNN
_d_h_c_p__b_o_o_t_p execution can be controlled through the following steps.
1) Specify the additional DHCP-related options in the
/_e_t_c/_c_o_n_f_i_g/_d_h_c_p__b_o_o_t_p._o_p_t_i_o_n_s file as follows:
----yyyy If you are using NIS to propagate the _h_o_s_t_s and _e_t_h_e_r_s map, this
system is required to be the NIS master server for _p_r_o_c_l_a_i_m to
work correctly.
----wwww _h_o_s_t_s__m_a_p
Specifies the optional location of the _h_o_s_t_s map. Not valid
with the ----ssss option. The default is /_e_t_c/_h_o_s_t_s.
PPPPaaaaggggeeee 1111
ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM)))) ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM))))
----eeee _e_t_h_e_r_s__m_a_p
Specifies the optional location of the _e_t_h_e_r_s map. Not valid
with the ----ssss option. The default is /_e_t_c/_e_t_h_e_r_s.
----uuuu _s_y_s_n_a_m_e
Specifies the name for an optional _s_y_s_n_a_m_e file. The default is
/_u_n_i_x.
----cccc _p_r_o_c_l_a_i_m__c_o_n_f_i_g__d_i_r
Specifies the optional proclaim server configuration directory.
The default directory is /_v_a_r/_d_h_c_p/_c_o_n_f_i_g.
----tttt _s_e_c_o_n_d_s
A timeout period for the _d_h_c_p__b_o_o_t_p server can be set else the
default period will be used.If a timeout period of 0 seconds is
used then the _d_h_c_p__b_o_o_t_p server will become a persistent daemon.
----xxxx This option is used in conjunction with a Domain Name Server
that provides the IP address to hostname mapping for the initial
assignment of IP addresses to hosts by the DHCP server. The
option has been found to be particularly useful in an Internet
Service Provider type of setup where the IP address to hostname
mapping may be required to remain fixed. Once an IP address is
assigned it is written to the _e_t_h_e_r_T_o_I_P._p_a_g file. When this
option is in effect, _e_t_h_e_r_T_o_I_P._p_a_g is the only file consulted to
determine whether a particular IP address or hostname is already
assigned.
----nnnn Specifies that the server should return a netmask with its reply
regardless of whether a client requested it or not.
----mmmm _o_p_t_i_o_n_s
Specifies additional options to be sent by the server to clients
irrespective of whether the client requests them or not. The
additional options are specified as a comma or colon separated
list with no spaces.
----rrrr _s_c_r_i_p_t__f_i_l_e__p_a_t_h
Specifies an optional script file to execute when the server
changes the _e_t_h_e_r_T_o_I_P database. The complete path to the script
must be specified as an a argument. The server calls the script
with several command-line arguments: -_c _c_l_i_e_n_t__i_d_e_n_t_i_f_i_e_r -_m
_p_h_y_s_i_c_a_l__a_d_d_r_e_s_s -_i _i_p__a_d_d_r_e_s_s -_h _h_o_s_t_n_a_m_e -_l _l_e_a_s_e -_o _o_p_e_r_a_t_i_o_n
-_t _d_h_c_p__m_e_s_s_a_g_e__t_y_p_e. The script is executed in the background.
The value of the operation argument is 0 if it was a record
creation, 1 if it was a deletion, and 2 if the lease was
updated. The dhcp_message_type is the same as defined message
types in the DHCP literature. If a message is sent to the client
that message type is passed as an argument, otherwise the
message type received from the client is passed. This script may
be used to perform other functions such as dynamic DNS updates.
PPPPaaaaggggeeee 2222
ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM)))) ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM))))
----WWWW Specifies that the the hosts map file or /_e_t_c/_h_o_s_t_s file should
not be updated when leases are added or removed.
----EEEE Specifies that the ethers map file or/_e_t_c/_e_t_h_e_r_s file should not
be updated when leases are added or removed.
The following options (----ppppnnnn,,,,----pppptttt,,,,----ppppllll) can be set only
with the Enhanced DHCP server product.
----ppppnnnn Specifies that a ping be sent before an address is leased to
check if a host is using the IP address. If a reply is received
then a message is logged in the SYSLOG indicating that "Address
<addr> appears to be STOLEN" and a record is added into the
database with a lease time of -2 for this IP address. The DHCP
administrator should investigate the occurrence and remove the
entry in the database with the _d_h_c_p_d_b command once it has been
resolved. The DHCP server tries to give out another address to
the requesting client.
----pppptttt _p_i_n_g__t_i_m_e_o_u_t
Specifies the timeout for the ping. If a reply to a ping is not
received in _p_i_n_g__t_i_m_e_o_u_t seconds the address is considered to be
not taken. The default value for the timeout is 1 second. Note
that the server processes requests from other DHCP clients while
waiting for the timeout to expire. The server does not block
waiting for a reply to a ping request. If blocking pings are
required for some reason use the ----ppppbbbb option instead of the ----ppppnnnn
option.
----ppppllll _n_u_m_b_e_r__o_f__o_u_t_s_t_a_n_d_i_n_g__p_i_n_g_s
This is the maximum number of pings outstanding. Once this value
is reached the server automatically stops sending ping to check
if an IP address is taken. The server begins to send ping
request once the number of outstanding ping requests falls below
this value. It is set to 16 by default.
2) Create one or more network configuration files based on the network
numbers this server is responsible for. A default configuration file
is provided: /_v_a_r/_d_h_c_p/_c_o_n_f_i_g/_c_o_n_f_i_g._D_e_f_a_u_l_t. The new file(s) should
be named _c_o_n_f_i_g.<_n_e_t_n_u_m_b_e_r> in the same directory. For example, if
this server is serving clients on the 192.26.61 network, the
configuration file should be named _c_o_n_f_i_g._1_9_2._2_6._6_1._0. See below for
a list of configuration parameters.
3) The DHCP server also provides MAC address based filtering. This
option is available only with the Enhanced DHCP server product. The
filters are specified in the /_v_a_r/_d_h_c_p/_c_o_n_f_i_g/_d_h_c_p_m_t_a_b file. MAC
addresses can be specified as either complete addresses or as a
regular expression to specify a set of addresses. The regular
expression syntax is described in the man pages for _r_e_g_c_m_p(_3_G).
If a DHCP packet from a client with a matching mac address is
PPPPaaaaggggeeee 3333
ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM)))) ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM))))
received then the corresponding actions are taken. Regular expression
matching is attempted only if a complete match is not found. The
length and hardware type must also match for non-regular expression
entries. The length may not match for entries that have regular
expressions. Once a match is found the remaining entries are not
searched. An example of the configuration file is as follows
# dhcpmtab - mac address based filtering for DHCP
#len htype mac action
6 1 01:02:03:8a:8b:8c K
0 1 01:02:* L|K
The actions can be specified as a combination of L and K. Each of the
actions L=log request, and K=drop request, is acted upon in that order.
The system log is updated if the L action is requested. If the K action
is specified and an L is not specified then the packet is silently
dropped.
4) Enable the _p_r_o_c_l_a_i_m server by giving the command:
cccchhhhkkkkccccoooonnnnffffiiiigggg pppprrrrooooccccllllaaaaiiiimmmm____sssseeeerrrrvvvveeeerrrr oooonnnn
5) Replace the "bootp" entry in /_u_s_r/_e_t_c/_i_n_e_t_d._c_o_n_f with this line:
bbbboooooooottttpppp ddddggggrrrraaaammmm uuuuddddpppp wwwwaaaaiiiitttt rrrrooooooootttt ////uuuussssrrrr////eeeettttcccc////ddddhhhhccccpppp____bbbboooooooottttpppp ddddhhhhccccpppp____bbbboooooooottttpppp ----oooo \\\\
////eeeettttcccc////ccccoooonnnnffffiiiigggg////ddddhhhhccccpppp____bbbboooooooottttpppp....ooooppppttttiiiioooonnnnssss
6) Issue this command, to restart _i_n_e_t_d with ////eeeettttcccc////kkkkiiiillllllllaaaallllllll ----HHHHUUUUPPPP iiiinnnneeeettttdddd:
_////_eeee_tttt_cccc_////_kkkk_iiii_llll_llll_aaaa_llll_llll _bbbb_oooo_oooo_tttt_pppp
CCCCoooonnnnffffiiiigggguuuurrrraaaattttiiiioooonnnn PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss
These parameters can be supplied in the configuration file for each
network. All of the address fields can either be in standard IP address
dot notation, or as a hex number prefixed with a 0x. Most of the fields
can be left blank to render them non-applicable.
_p_r_o__a_d_d_r_e_s_s__c_o_u_n_t_e_r
This integer field specifies the host number for the next IP
address. The next address is constructed using the counter and
checked through the range of the assignable addresses. The first
available address in the range is assigned.
_p_r_o__h_o_s_t__p_f_x__c_o_u_n_t_e_r
This integer field specifies the starting number appended to the
_p_r_o__h_o_s_t__p_r_e_f_i_x to generate a new hostname. This counter is
incremented and a new hostname generated until a unique unused name
is found.
_p_r_o__n_e_t_m_a_s_k
This field takes a netmask in address form. For more information on
netmasks, see the _I_R_I_X _A_d_m_i_n: _N_e_t_w_o_r_k_i_n_g _a_n_d _M_a_i_l guide. This field
PPPPaaaaggggeeee 4444
ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM)))) ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM))))
specifies the subnetmask used by the client systems.
_p_r_o__l_e_a_s_e
This unsigned integer field specifies the client address lease time
in seconds. This implementation of the DHCP server assigns 3 year
leases by default, and the leases are expired only when explicitly
surrendered by the client.
_p_r_o__h_o_s_t__p_r_e_f_i_x
This string field specifies the default text prefix for generating
client hostnames. For example, the prefix iiiirrrriiiissss directs proclaim to
generate hostnames of the form iiiirrrriiiissss1111, iiiirrrriiiissss2222, iiiirrrriiiissss3333, and so on.
_p_r_o__c_h_o_o_s_e__n_a_m_e
This boolean (true or false) flag specifies whether the client
systems are allowed to choose their own hostname or whether they
must be assigned the name given to them by the server. A value of 1
(true) in this field brings up a dialog box on the client system
giving the user the option of either taking the name offered by the
server or entering a hostname of the user's choice. If the user
selects a name, the server allows this name if it passes basic tests
for syntax and uniqueness, otherwise the server/client dialogue
continues until a mutually acceptable name is submitted. A value of
0 (false) in this field indicates that the user on the client system
must accept the name provided by the server.
_p_r_o__i_p_a_d_d_r_e_s_s__r_a_n_g_e
This field takes an entry of integers using standard numeric range
rules. The entry defines the range of host number addresses
assignable by this server. For example, if the value is: 1-3, 5-7,
9. The server issues IP addresses with the base address specified
in the configuration filename (such as _c_o_n_f_i_g._1_9_2._2_6._6_1._0).
Each client is issued an IP address matching the name of the
configuration file, suffixed with the numbers 1 through 3, and 5
through 7, and 9, but not 4 or 8. This option can be to restrict
the IP addresses offered by a given server. This is very useful if
the administrator wants to assign only certain block(s) of addresses
using proclaim, or in the absence of a server to server protocol,
wishes to have multiple servers serve clients on the same subnet.
_p_r_o__r_o_u_t_e_r__a_d_d_r
This field of comma-separated IP addresses specifies a list of
addresses for network routers on the client's subnet. Routers
should be listed in the order of preference for their use.
_p_r_o__b_o_o_t_f_i_l_e__s_i_z_e
Specifies length in 512-octet blocks of the default boot image for
the client.
PPPPaaaaggggeeee 5555
ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM)))) ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM))))
_p_r_o__t_i_m_e__o_f_f_s_e_t
Specifies offset of the client's subnet from Coordinated Universal
Time (UTC) in seconds.
_p_r_o__m_e_r_i_t_d_u_m_p__p_a_t_h_n_a_m_e
Specifies a file for dumping a core image in case the client
crashes.
_p_r_o__r_o_o_t__p_a_t_h_n_a_m_e
Specifies the directory that contains the client's root disk
partition.
_p_r_o__e_x_t_e_n_s_i_o_n_s__p_a_t_h_n_a_m_e
Specifies a TFTP file containing vendor extensions for _b_o_o_t_p. On
SGI systems the this file has the same format as the
_c_o_n_f_i_g._n_e_t_n_u_m_b_e_r file.
_p_r_o__T_F_T_P_s_e_r_v_e_r__n_a_m_e
Specifies a TFTP server for the client.
_p_r_o__b_o_o_t_f_i_l_e__n_a_m_e
Specifies the pathname of the default boot image for the client.
_p_r_o__d_n_s__d_o_m_a_i_n
This text field specifies the domain name that client should use
when resolving hostnames using DNS.
_p_r_o__d_n_s_s_e_r_v_e_r__a_d_d_r
This field of comma-separated IP addresses specifies a list of
addresses for Domain Name System servers available to the client.
Servers should be listed in the order of preference for their use.
_p_r_o__p_r_o_p_e_l__s_e_r_v_e_r
This IP address specifies the address of the _p_r_o_p_e_l server that
serves the clients on this subnet. Additional information about
_p_r_o_p_e_l can be found in Chapter 2, "Software Distribution, User, and
Host Management With propel," of the _I_R_I_X_p_r_o _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e.
_p_r_o__t_i_m_e_s_e_r_v_e_r__a_d_d_r
This field of comma-separated IP addresses specifies a list of
addresses for time servers available to the client. Addresses
should be listed in the order of preference for their use.
_p_r_o__l_o_g_s_e_r_v_e_r__a_d_d_r
Specifies a list of UDP log servers available to the client.
_p_r_o__c_o_o_k_i_e_s_e_r_v_e_r__a_d_d_r
Specifies a list of RFC 865 cookie servers available to the client.
_p_r_o__L_P_R_s_e_r_v_e_r__a_d_d_r
Specifies a list of RFC 1179 line printer servers available to the
client.
PPPPaaaaggggeeee 6666
ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM)))) ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM))))
_p_r_o__r_e_s_o_u_r_c_e_s_e_r_v_e_r__a_d_d_r
Specifies a list of RFC 887 resource location servers available to
the client.
_p_r_o__s_w_a_p_s_e_r_v_e_r__a_d_d_r
Specifies the IP address of the client's swap server.
_p_r_o__n_i_s__d_o_m_a_i_n
This text field specifies the name of the client's NIS domain.
_p_r_o__n_i_s_s_e_r_v_e_r__a_d_d_r
This field of comma-separated IP addresses specifies a list of
addresses indicating NIS servers available to the client. Servers
should be listed in the order of preference for their use.
_p_r_o__m_t_u
This unsigned short integer field specifies the MTU (maximum
transmission unit) to use on the network interface configured in
this file. The minimum legal value for the MTU is 68.
_p_r_o__a_l_l_n_e_t_s__l_o_c_a_l
This boolean (true/false) field specifies whether or not the client
can assume that all other subnets of the IP network to which the
client is connected use the same MTU as the subnet to which the
client is directly connected. A value of 1 (true) indicates that
all subnets share the same MTU. A value of 0 (false) means that the
client should assume that some other subnets can have smaller MTUs.
_p_r_o__b_r_o_a_d_c_a_s_t
This IP address field specifies the broadcast address in use on the
client's subnet.
_p_r_o__d_o_m_a_s_k__d_i_s_c
This boolean (true/false) Perform Mask Discovery field specifies
whether or not the client should perform subnet mask discovery using
ICMP. A value of 1 (true) means that the client should perform mask
discovery, while a value of 0 (false) indicates that the client
should not perform mask discovery.
_p_r_o__r_e_s_p__m_a_s_k__r_e_q
This boolean (true/false) Mask Supplier field specifies whether or
not the client should respond to subnet mask requests using ICMP. A
value of 1 (true) means that the client should respond. A value of
0 (false) in this field means that the client should not respond.
_p_r_o__s_t_a_t_i_c__r_o_u_t_e_s
This field takes a comma-separated list of routes in the following
form:
ddddeeeesssstttt____aaaaddddddddrrrreeeessssssss ---- rrrroooouuuutttteeeerrrr____aaaaddddddddrrrreeeessssssss,,,, ddddeeeesssstttt____aaaaddddddddrrrreeeessssssss2222 ---- rrrroooouuuutttteeeerrrr____aaaaddddddddrrrreeeessssssss2222....
The static route field specifies a list of static routes that the
client should install in its routing cache. If multiple routes to
the same destination are specified, they should be listed in
PPPPaaaaggggeeee 7777
ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM)))) ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM))))
descending order of priority. The routes consist of a list of IP
address pairs. The first address is the destination address; its
counterpart address, separated by a dash (-), is the address of the
router to the destination. The default route (0.0.0.0) is an
illegal destination for a static route.
_S_e_r_v_e__T_h_i_s__N_e_t_w_o_r_k
Toggle DHCP serving of this subnet.
_O_t_h_e_r _O_p_t_i_o_n_s
The Proclaim server also handles other options listed in RFC 1533.
To set values for these options use of the _P_r_o_c_l_a_i_m_S_e_r_v_e_r_M_g_r(1M)
graphical user interface is recommended. You can view the standard
_c_o_n_f_i_g._D_e_f_a_u_l_t file in the /_v_a_r/_d_h_c_p/_c_o_n_f_i_g directory to see all the
supported options.
The following are the active lines only from a working _c_o_n_f_i_g._n_e_t_n_u_m_b_e_r
configuration file:
Serve_This_Network: 1
pro_address_counter: 1
pro_host_pfx_counter: 1
pro_netmask: 255.255.255.0
pro_lease: 604800
pro_host_prefix: n6634
pro_choose_name: 1
pro_ipaddress_range: 1-254
pro_dns_domain: engr.sgi.com
pro_nis_domain: engr.sgi.com
pro_mtu: 1500
pro_allnets_local: 1
pro_domask_disc: 0
pro_resp_mask_req: 0
NNNNOOOOTTTTEEEESSSS
Debugging may be enabled by sending a SIGUSR1 signal to the server and
may be disabled by sending SIGUSR2. To increase the level of debugging
send multiple SIGUSR1 signals, for example, kkkkiiiillllllllaaaallllllll ----UUUUSSSSRRRR1111 ddddhhhhccccpppp____bbbboooooooottttpppp.
The dhcp_bootp server database is maintained in ndbm files with (.dir)
and (.pag) extensions.The /_u_s_r/_s_b_i_n/_d_b_m_T_o_E_t_h_I_P utility can be used to
view the contents of this file. It converts the ndbm format to the text
format and outputs the text onto the standard output.In case of
situations where it is needed to generate the ndbm files the
/_u_s_r/_e_t_c/_e_t_h_I_P_T_o_D_b_m utility may be used to convert a _e_t_h_e_r_T_o_I_P file (in
text format) to ndbm formatted files.
To use the _b_o_o_t_p server with DHCP style options specify the options in
the /_e_t_c/_c_o_n_f_i_g/_b_o_o_t_p-_r_f_c_1_5_3_3._o_p_t_i_o_n_s file. See this file to check what
options are supported.
PPPPaaaaggggeeee 8888
ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM)))) ddddhhhhccccpppp____bbbboooooooottttpppp((((1111MMMM))))
FFFFIIIILLLLEEEESSSS
/etc/config/dhcp_bootp.options
/etc/config/bootp-rfc1533.options
/etc/hosts
/etc/ethers
/usr/etc/inetd.conf
/var/dhcp/etherToIP
/var/dhcp/etherToIP.pag
/var/dhcp/etherToIP.dir
/var/dhcp/config/config.Default
/var/dhcp/config/dhcpmtab
SSSSEEEEEEEE AAAALLLLSSSSOOOO
bootp(1M), chkconfig(1M), dhcp_relay(1M), inetd(1M), proclaim(1M),
ProclaimServerMgr(1M), syslogd(1M), ethers(4), hosts(4).
IETF RFCs 1541, 1533, 1534, 1535.
PPPPaaaaggggeeee 9999